ols (headings: chapter, section, etc.)
>> * Spell-checking of body text and section titles
>> * Managing builds with Nova's tasks system
>>
>> (As an aside, this extension uses an updated version of the ConTeXt
>> tree-sitter parser [https://github.com/pmazaitis/tree-sitte
nts
> * Navigating by Symbols (headings: chapter, section, etc.)
> * Spell-checking of body text and section titles
> * Managing builds with Nova's tasks system
>
> (As an aside, this extension uses an updated version of the ConTeXt
> tree-sitter parser [https://github.com/pmazaitis/
On Sat, 11 Nov 2023, Paul Mazaitis wrote:
I don't use MacOS, but ...
> (As an aside, this extension uses an updated version of the ConTeXt
> tree-sitter parser [https://github.com/pmazaitis/tree-sitter-context] that
> can now recognize (most) environments and use them to parse out the
functional.
This version of the extension supports:
* Syntax Highlighting
* Folding for (most) environments
* Navigating by Symbols (headings: chapter, section, etc.)
* Spell-checking of body text and section titles
* Managing builds with Nova's tasks system
(As an aside, this extension uses
supports:
* Syntax Highlighting
* Folding for (most) environments
* Navigating by Symbols (headings: chapter, section, etc.)
* Spell-checking of body text and section titles
* Managing builds with Nova's tasks system
(As an aside, this extension uses an updated version of the ConTeXt tree-sitter
parser
My feeling at the moment is that this might be about the only way one
could go ahead in a production situation, and yes, I am familiar with
PDF tools that can achieve this, though it is effectively stepping aside
from ConTeXt and working with PDF. For that matter I can easily go ahead
?
Using the key does not seem to work.
As an aside, I've tried to use the < command > key to provide my own command,
but while \define works here (but ignores \blank), \def gives me an error.
Why is that?
How would you add blanks to a user-defined command?
Best,
Denis
\setuphead[c
Hi,
is it possible to access a structureuservariable before the heading's title ?
Using the key does not seem to work.
As an aside, I've tried to use the < command > key to provide my own command,
but while \define works here (but ignores \blank), \def gives me an error.
Why is that?
How
as
getting even less tracing clutter (the kind of changes for Wolfgang to
check -)
- as aside effect there is some performance gain (there is not that
much more to gain now unless we go ugly); this all depends on usage of
course
- at some point some of the more obscure middle level helpers (dating
ontext] new upload
>
> Hi,
>
> No functional changes this time:
>
> - some more consistent usage of new primitives instead of helper macros, also
> a bit of a look and feel related effort as well as getting even less tracing
> clutter
> (the kind of changes for Wolfgang to
Hi,
No functional changes this time:
- some more consistent usage of new primitives instead of helper macros,
also a bit of a look and feel related effort as well as getting even
less tracing clutter (the kind of changes for Wolfgang to check -)
- as aside effect there is some performance
to have, say, a control _word_ such as \TeX\, the sequence of
> > > TeX kerning is thrown off. The only remedy would be to have a a \qquad
> > > preceding the control sequence e.g., {\qquad
> > > \TeX\ significantly} to sort of ameliorate this side-effect. But then
> >
and spaces would
> > display what's to be expected. And yet, the aformentioned set of
> >
> > tSP:3.282
> > THK:-1.721
> > H__E
> > X
> > HK:-1.291
> > SP:3.282
> >
> > is accurate nevertheless. And a very nice implementation at that,
> &
ice implementation at that,
but one I fear can't be included on a final document either.
With that being said, the introduction of a \qquad, in addition to
\showmakeup with, say, redundancy aside, whatever is preceding the \TeX\
alongside the file would also introduce a space where no space was e
But it's interesting that \showmakeup, kerning and spaces would
> > display what's to be expected. And yet, the aformentioned set of
> >
> > tSP:3.282
> > THK:-1.721
> > H__E
> > X
> > HK:-1.291
> > SP:3.282
> >
> > is accurate nevertheles
291
> SP:3.282
>
> is accurate nevertheless. And a very nice implementation at that,
> but one I fear can't be included on a final document either.
>
> With that being said, the introduction of a \qquad, in addition to
> \showmakeup with, say, redundancy aside, whatever is
aside, whatever is preceding the \TeX\
alongside the file would also introduce a space where no space was ever
there before.
Because of all of this, and unfortunately, \showmakeup is not quite helpful
here either. Although it does so displays the amount of spaces and
so forth, any addition
lmtx uses but by just looking at the bare
macros, it seems as if `\forgetplaceinitial` is limited in what it can
and can't do. I think it's reasonable the way it was implemented but
nevertheless this is something that ought to be looked at rather than
ignore it or put aside for later
I didn'
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
> > Hello list:
> >
> > This is under a fresh TeXLive installation. Sort as to put aside any
> > texlive prepackaged issues.
>
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
> > Hello list:
> >
> > This is under a fresh TeXLive installation. Sort as to put aside any
> > texlive prepackaged issues.
>
setting in place.. or much less —
regardless of fonts' location, that a program out there needs to act
erratically. Careless. To say the least. Bear with me in this one (I'm just a
bit tired):
Look at the same issue from another system perspective. I said system
perspective because simply put
On Sat, Mar 25, 2023 at 09:26:36PM +0100, Hans Hagen via ntg-context wrote:
> On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
> > Hello list:
> >
> > This is under a fresh TeXLive installation. Sort as to put aside any
> > texlive prepackaged issues.
>
On 3/25/2023 8:55 PM, Carlos via ntg-context wrote:
Hello list:
This is under a fresh TeXLive installation. Sort as to put aside any texlive
prepackaged issues.
And the followign lines is the output of the error I've been having with the
call of context on a recent texlive installation
Hello list:
This is under a fresh TeXLive installation. Sort as to put aside any texlive
prepackaged issues.
And the followign lines is the output of the error I've been having with the
call of context on a recent texlive installation by both mtxrun --generate and
luatools --generate right
project.
What are the things I am interested in most?
I would like to take an intensive training.
Aside from the core functions I would like to learn more about
integrations as this is what we are trying to do at Hostsharing at the
moment. This could cover small things like automated
an intensive training.
Aside from the core functions I would like to learn more about
integrations as this is what we are trying to do at Hostsharing at the
moment. This could cover small things like automated business graphics
with different tools to printing from TEI-XML to setup a single source
On 7/20/2022 9:40 PM, Bruce Horrocks via ntg-context wrote:
On 20 Jul 2022, at 05:31, Michael Urban via ntg-context
wrote:
Aside from purchasing a real font product from Linotype at enormous expense and
hoping it is better equipped, is there a way to coerce ConTeXt into using
> On 20 Jul 2022, at 05:31, Michael Urban via ntg-context
> wrote:
>
> Aside from purchasing a real font product from Linotype at enormous expense
> and hoping it is better equipped, is there a way to coerce ConTeXt into using
> the ligature glyphs for fi and fl?
Yes - I
On 7/20/2022 6:31 AM, Michael Urban via ntg-context wrote:
I downloaded something that purports to be Century Expanded from fontsgeek.com.
Although the font has fi and fl ligature glyphs, it does not have a ligature
font feature and ConTeXt does not use those glyphs.
Aside from purchasing
I downloaded something that purports to be Century Expanded from fontsgeek.com.
Although the font has fi and fl ligature glyphs, it does not have a ligature
font feature and ConTeXt does not use those glyphs.
Aside from purchasing a real font product from Linotype at enormous expense
Thanks for your suggestions.
It probably is not EXIF-related. I've opened and saved the image with MS Paint,
but that did not change anything (the increase in file size aside...).
Any other ideas? (I tend to think the image is corrupted in one way or the
other, but I have no clue how to fix
w in (VAR .. ";"):gmatch("([^;]*);") do ...
Splitting 'w' afterwards on the colon within key:value pairs would still be
necessary, so maybe that approach is a wash.
Aside, when I made changes to the file, I couldn't get either a report() or
a print() statement to show up in
Betreff: Re: [NTG-context] Citeproc-lua
On 5/6/2022 11:02 PM, Denis Maier via ntg-context wrote:
> I also have the impression that extending citeproc-formats.lua should be the
> easiest part. As an aside, I think the HTML is in there because that is
> needed for the test suite, but for C
On 5/6/2022 11:02 PM, Denis Maier via ntg-context wrote:
I also have the impression that extending citeproc-formats.lua should be the
easiest part. As an aside, I think the HTML is in there because that is needed
for the test suite, but for ConTeXt we should be able to copy the LaTeX mapping
, but anyway...
I also have the impression that extending citeproc-formats.lua should be the
easiest part. As an aside, I think the HTML is in there because that is needed
for the test suite, but for ConTeXt we should be able to copy the LaTeX mapping
and tweak a few things here and there.
The LaTeX
ession that extending citeproc-formats.lua should be the
> easiest part. As an aside, I think the HTML is in there because that is
> needed for the test suite, but for ConTeXt we should be able to copy the
> LaTeX mapping and tweak a few things here and there.
>
> The LaTeX pac
Hi,
thanks for your assessment. Indeed, that looks very promising.
I've now had a chance to look at this a bit more too. Not that I understand
that stuff in detail, but anyway...
I also have the impression that extending citeproc-formats.lua should be the
easiest part. As an aside, I think
a tiny detail I am missing, but I think, if I keep going at
this pace, I will end up learning it by heart.
Well, joking aside, thanks again for your advice, Max.
Edu.
El 26/4/22 a las 4:42, Max Chernoff escribió:
On 2022-04-25 6:51 p.m., Eduardo Bohoyo wrote:
First things first. I want to acknowl
ase of the broken scripts is even stranger: only two of
the six breakages concern a couple of those early chapter pages.
I will go over the lua-widow-control.pdf document once more in case
there is a tiny detail I am missing, but I think, if I keep going at
this pace, I will end up learning it by
\startformula
a = \frac{ b + \mu }{ c }
\stopformula
\startformula
a = \frac{\frac{ b + \mu }{ c } + e}{ d + i }
\stopformula
\stoptext
Thank you very much for the hints. \frac didn't help either even after
moving broken installation aside and doing a fresh install with
sh
\startformula
> a = \frac{ b + \mu }{ c }
> \stopformula
>
> \startformula
> a = \frac{\frac{ b + \mu }{ c } + e}{ d + i }
> \stopformula
> \stoptext
>
Thank you very much for the hints. \frac didn't help either even after
moving broken installation aside
On Tuesday, March 29, 2022 4:18 AM Michael Urban via ntg-context wrote:
> Is there a simple way to accomplish this?
Aside from the other solution using makeup, a simpler way might be to just use
the 'page' option for positioning the float. The following MWE achieves the
same res
e other than "thanks" does not
> > work, and I have no clue why. Am I missing something, or is there a more
> > elegant way to implement this?
> >
> > As an aside, I'd rather have the footnotes below the "thanks" notes. Is
> > there any option that d
://wiki.contextgarden.net/LaTeX_Thanks). However, one thing that
bugs me is that any note name I choose other than "thanks" does not
work, and I have no clue why. Am I missing something, or is there a more
elegant way to implement this?
As an aside, I'd rather have the footnotes below the &quo
note name I choose other than "thanks" does not work, and I
have no clue why. Am I missing something, or is there a more elegant way to
implement this?
As an aside, I'd rather have the footnotes below the "thanks" notes. Is
there any option that does this?
\setuplist[se
Marco
Thanks a lot. It works. Such a solution had briefly crossed my mind but I
had left it aside, hoping there was some feature I had missed.
Em qua., 29 de dez. de 2021 10:40, Marco Patzer via ntg-context <
ntg-context@ntg.nl> escreveu:
> On Wed, 29 Dec 2021 08:29:34 -0300
> Yo
that bugs
me is that any note name I choose other than "thanks" does not work, and I
have no clue why. Am I missing something, or is there a more elegant way to
implement this?
As an aside, I'd rather have the footnotes below the "thanks" notes. Is
there any option tha
as
a result. Look at the definition. If the current fontalternative is it \it it
will give a \tf result. It is sensitive to the current state in a similar way
that \em and \emph are, but it will always give an italic or roman result.
If we leave the comparisons between \em and \italicface aside
t;> as a result. Look at the definition. If the current fontalternative is it
>> \it it will give a \tf result. It is sensitive to the current state in a
>> similar way that \em and \emph are, but it will always give an italic or
>> roman result.
>>
>
> If we leave
state in a similar way that \em and \emph are, but it
will always give an italic or roman result.
If we leave the comparisons between \em and \italicface aside and talk
only about the results from \italicface we have a common ground.
You're right the results from \italicface aren't
ixed one
potential source of the problem, and I’m currently functioning fine, I think
I’ll set this aside for now and get some work done. When I have a little more
time, I will try updating the modules again and compare the files to the
current version of TikZ. Then, if everything is great, I’ll
On 5/10/2021 8:42 AM, Pablo Rodriguez wrote:
On 5/9/21 7:46 PM, Hans Hagen wrote:
[...]
you can also retest the advance
It works fine now.
A minor issue happens with SumatraPDF-3.1.2 (aside from font advance):
Works fine with 3.3.13 here. (btw, if after decades of pdf viewers still
don't
On 5/9/21 7:46 PM, Hans Hagen wrote:
> [...]
> you can also retest the advance
It works fine now.
A minor issue happens with SumatraPDF-3.1.2 (aside from font advance):
\setuppapersize[A6]
\definefontfamily[mainface][rm]
[TeX Gyre Pagella]
\setupbodyfont[mainface]
\sta
that the #Forced_Page_break reference in the wiki simply
no longer applies in any situation? Anyway, that aside, thank you for
the solution.
Julian
On 6/10/20 9:38 am, Willi Egger wrote:
Hello Julian,
the mechanism does not work in the typesetting of the TOC.
Whatt you is the following, when the book is in a final
shows that some things don't change in ConTeXt :-)
Kidding aside, why is there a difference between the tabulate mechanism and the
xtable mechanism?
Best regards: Otared K.
___
If your question is of interest to
as a
>> > first step? Thank you very much.
>> I admit that I have no clue about what xetex does in that departmentbut
>> you're right that in lmtx the vertical directions are not supported. The
>> main reason is that it didn't really integrates well in the way pages
>>
mtxrun | unknown script 'fonts.lua' or
> > 'mtx-fonts.lua'
>
> The same question was asked a few days ago:
>
> https://www.mail-archive.com/ntg-context@ntg.nl/msg95227.html
>
> The solution was to refresh the database: luatools --generate
>
>
script 'fonts.lua' or
'mtx-fonts.lua'
The same question was asked a few days ago:
https://www.mail-archive.com/ntg-context@ntg.nl/msg95227.html
The solution was to refresh the database: luatools --generate
Aside from luatools you can also use mtxrun to refresh the database
(mtxrun --generate
le is made available in luametatex) But especially the mode
field sometimes has values which do not correspond to the mode of
the actual primitives:
indeed.
I tried running the following in an almost iniTeX setting where all
primitives aside from \shipout and \Umathcodenum have the
k it is awesome that such a
table is made available in luametatex) But especially the mode
field sometimes has values which do not correspond to the mode of
the actual primitives:
I tried running the following in an almost iniTeX setting where all
primitives aside from \shipout and \Um
and macro package.
Already for quite a while there are the basics for a more advanced
vertical subsystem but it's typically one of these things that I explore
and then set aside till some users show up who need it and are willing
to spend time on discussing and testing intertfaces. After all
could adjust that to something like 1cm instead
of 4cm.
The problem is that when I try to process the original example, I get
a fatal error at the line which reads \chapter{test} \input tufte.
I'm not sure why that error, but that aside, would the
\def\MyChapterCommand approach suggested
is that when I try to process the original example, I get a
fatal error at the line which reads \chapter{test} \input tufte.
I'm not sure why that error, but that aside, would the
\def\MyChapterCommand approach suggested above be the right way to
achieve my purpose? In other words, I want the text
example, I get a
fatal error at the line which reads \chapter{test} \input tufte.
I'm not sure why that error, but that aside, would the
\def\MyChapterCommand approach suggested above be the right way to
achieve my purpose? In other words, I want the text that follows the
chapter title to follow
extra files generated by automatic EPS to
PDF conversion (with figures.cachepaths.prefix="\jobname-temp"), etc.
As an aside, I also noticed that in both mkiv and lmtx, mtx-context.lua has
local extra_runfiles = {
"^l_m_t_x_.-%.pdf$",
}
but graph-inc.lua has
to PDF conversion (with
figures.cachepaths.prefix="\jobname-temp"), etc.
As an aside, I also noticed that in both mkiv and lmtx, mtx-context.lua has
local extra_runfiles = {
"^l_m_t_x_.-%.pdf$",
}
but graph-inc.lua has
local defaultprefix = "m_k_i_v_"
S
="\jobname-temp"), etc.
As an aside, I also noticed that in both mkiv and lmtx, mtx-context.lua has
local extra_runfiles = {
"^l_m_t_x_.-%.pdf$",
}
but graph-inc.lua has
local defaultprefix = "m_k_i_v_"
So, the default generated fi
that was my mistake. :-(
> You have a problem here (aside from broken formatting). The 'mtxrun'
> didn't find necessary files, take a look on last part of output.
Clash with texlive's luatex engine installed before...
Thank you for taking time. ;)
Sincerely,
Gour
--
A person who
2c' from specification
> 'selfautoparent:/texmf-dist/web2c' resolvers | resolving |
> looking for fallback 'contextcnf.lua' on given path
> '/home/gour/opt/texmf/web2c' from specification
> 'selfautoparent:/texmf/web2c' resolvers | resolving | resolvers
> | resol
On 1/17/2020 8:11 PM, Wolfgang Schuster wrote:
It's possible to use leaders to remove multiple dashes and also dashes
at the end of a paragraph but this will only work for the PDF. A
limitation is that you can't use the existing \speech and \aside
commands because they use groups which
of paragraphs.
\endash~he continued.
\stopsection
\startsection[title=Actual output]
\speech{Speech should always have a dash at the start, but none at the
end of a
paragraph.}
\speech{Dialog asides should not duplicate dashes, \aside{he said.}}
Also, note
the spacing isn't removed despite \type
continued.
\stopsection
\startsection[title=Actual output]
\speech{Speech should always have a dash at the start, but none at the
end of a
paragraph.}
\speech{Dialog asides should not duplicate dashes, \aside{he said.}}
Also, note
the spacing isn't removed despite \type{\removeunwantedspaces
(though still not most common) isn't as out of place.
See attachment for actual examples, but I'm looking for a dash at each side of
the quotation, /except/ at the very end of a paragraph. I additionally want
dialogue tags (via \aside, and located within quotations) to not print
Hello,
I'm trying to get four small A6 pages on one A4 page (portrait) like this:
4 1
3 2
The last two pages should be upside down.
This is my starting point:
\setuppapersize[A6][A4]
\setuparranging[1*4]
Aside from the different page sequence, this rotates the last two pages, which
Dear TeXies,
registrations are open (for some time already) so:
"The time has come for all good women and men
to come to the aid of BachoTeX 2019"
Well, jokes aside -- the deadline for registrations is
on the 31st of March, thus please hurry to take the
advantage of early ra
r TeXies,
>
> registrations are open (for some time already) so:
>
> "The time has come for all good women and men
> to come to the aid of BachoTeX 2019"
>
> Well, yokes aside -- the deadline for registrations is
> on the 31st of March, thus pleas
; appears to be overkill. For the declaration
>
> \setupdirections[bidi=global]
>
> shouldn't that mean that bidi is applied, well, globally?
>
> For \definedfont the behavior is less surprising, since that is obviously
> a local command. But is setups the official way to glob
idi=global]
shouldn't that mean that bidi is applied, well, globally?
For \definedfont the behavior is less surprising, since that is obviously
a local command. But is setups the official way to globalize the command
(aside from typescripts or simplefonts)?
Best wishes
Idris
On 20 Jun 2018
On 1/12/2018 6:44 PM, Rik Kabel wrote:
Bump.
This has come up a few times, but never resolved.
Is there the possibility of an option for placefigure to discard
remaining depth at a page break?
it's more a aside effect of operating at the edge of the page (i'm
reluctant to change
s not yet a version for MacOS? If I am right I
cannot find files for MacOS at your link above. Then I will wait and typeset my
files on Windows until the new version is released.
Mathias
> But aside from that. If you (developers, not users) want to call one
> version of LuaTeX 1.05, you
with outdated
timestamps of generated files. I'm waiting for Luigi to fix the
problem.
i'm somewhat puzzled by timestamps as i can compile here on my machine
(which has a rather limited linux box)
But aside from that. If you (developers, not users) want to call one
version of LuaTeX 1.05, you should tag
tdated
timestamps of generated files. I'm waiting for Luigi to fix the
problem.
But aside from that. If you (developers, not users) want to call one
version of LuaTeX 1.05, you should tag a version 1.05.
Increasing the version numbers in trunk and skipping any official
releases is a pretty bad deve
the advantage of both. When someone is accessing an
example that has e.g. the tags "table" and "luatex", then links to the
pdf and wiki documentation about tables and luatex could be shown aside.
And thanks for pointing that ! I would not have think about that otherw
; \starttikzpicture
>> \node {\color[red]{red}};
>> \node[xshift=30] {\color[red]{not red}};
>> \stoptikzpicture
>> \stoptext
>>
>> Can anybody tell me why the second node is not colored red?
>>
>> Aside: In LaTeX when using \color{red}{.
why the second node is not colored red?
Aside: In LaTeX when using \color{red}{...} this tikzpicture renders
correctly. For LaTeX I use TikZ version 3.0.1a, in ConTeXt it seems to
be version 3.0.1.
Any feedback is welcome.
tikz has its own color mechanisms and they don't mix well with context
Dear List,
I use the latest version of ConTeXt and I have the following MWE:
\usemodule[tikz]
\starttext
\starttikzpicture
\node {\color[red]{red}};
\node[xshift=30] {\color[red]{not red}};
\stoptikzpicture
\stoptext
Can anybody tell me why the second node is not colored red?
Aside
e using
Junction font).
(As an aside, is it also possible to combine \sc\bf? I haven't been
able to figure that out).
My application is using the (free) Andada font family, and I need to
point the smallcaps style to the correct font
(https://www.fontsquirrel.com/fonts/andada).
In the follo
I'm still a bit at a loss on how one goes about correctly specifying the
variants in \definefontfamily using the default form given in the wiki.
Usually adding "* Light", etc. is sufficient (see commented line using
Junction font).
(As an aside, is it also possible to combine
One can obtain language-dependent marking for sub-sentences through the
use of |<| this is an aside |>| or through the command
\startsubsentence ... \stopsubsentence or the (depreciated?)
\subsentence{...}.
I have several questions, and the source code appears to hold traces of
previou
ng \math{x^2} clearly states what it
is. TeX tradition aside, dollar signs make no sense here and you
have to manually match beginning and end. Braces are matched
automatically (probably depends on the editor as well).
\math{x²} states what it is. However \m{x²} is cryptic and, although
only tw
ce
>>> math should appear rather as displayed math.
>>
>> While I agree on that one, writing \math{x^2} clearly states what it
>> is. TeX tradition aside, dollar signs make no sense here and you
>> have to manually match beginning and end. Braces are matched
>>
s what it
is. TeX tradition aside, dollar signs make no sense here and you
have to manually match beginning and end. Braces are matched
automatically (probably depends on the editor as well).
Marco
___
If your qu
which one might want to have a reference
> math should appear rather as displayed math.
While I agree on that one, writing \math{x^2} clearly states what it
is. TeX tradition aside, dollar signs make no sense here and you
have to manually match beginning and end. Braces are matched
automat
On Sat, 25 Apr 2015 13:19:47 -0600, Pablo Rodriguez oi...@gmx.es wrote:
[Aside: I wonder if there is a way in ConTeXt to setup \placefootnotes
etc. in a mode so that it gets invoked only in the export. Will explore
this for the article.]
How about the system mode: \doifmode{*export
the footnotes
as endnotes. At the end of, e.g., a blog post you'll have a section for
footnotes/endnotes. In the context source I had to make a derivative
version and use something like
\startsubsubject[title=Endnotes]
\placefootnotes
\stopsubsubject
[Aside: I wonder if there is a way
On Sat, 25 Apr 2015 13:19:47 -0600, Pablo Rodriguez oi...@gmx.es wrote:
[Aside: I wonder if there is a way in ConTeXt to setup \placefootnotes
etc. in a mode so that it gets invoked only in the export. Will explore
this for the article.]
How about the system mode: \doifmode{*export
/endnotes. In the context source I had to make a derivative
version and use something like
\startsubsubject[title=Endnotes]
\placefootnotes
\stopsubsubject
[Aside: I wonder if there is a way in ConTeXt to setup \placefootnotes
etc. in a mode so that it gets invoked only in the export. Will explore
, particularly for long blog posts.]
Is there already a way to get done automatically?
In any case: This feature is a must-do in my humble opinion. Aside
from a
few other export bugs, this is one of the few features still needed so
that ConTeXt can completely replace markdown
to get the output to do what we
wanted.
[Also note that it makes much more sense to export the footnotes as
endnotes, particularly for long blog posts.]
Is there already a way to get done automatically?
In any case: This feature is a must-do in my humble opinion. Aside from a
few other export
fonts --reload' ...)
I installed these (otf) fonts systemwide.
(as an aside: is there a way of notifying standalone context of the
location of the `texlive' font directories?)
4.
contrary to what I seem to have read in the documentation somewhere (??)
the fonts were than _not_ looked up
1 - 100 of 214 matches
Mail list logo
